Jenkins CI known issues.

@jajanusz Btw, do you know if all your team are on GCC 9.x now ? We had some similar fixes last week due to folks updating compiler.

@jajanusz Btw, do you know if all your team are on GCC 9.x now ? We had some similar fixes last week due to folks updating compiler.

I doubt anyone is using it here. We mostly have gcc 7/8 on our setups.

@lgirdwood this PR broke UTs in CI, probably you 'fixed' some dirty hack for another issue ;)

@lgirdwood @marc-hb UTs are failing with this patch. The second test should be commented-out/removed to be consistent with the original change instead of being reactivated with no result verification.

@mmaka1 I just realized "Internal Intel CI System/merge/build — Unit tests failed" (a.k.a. "quickbuild") was not reported at all here, any idea why? They were reported in (unrelated) PR #2581 so I took them for granted.

The second test should be commented-out/removed to be consistent with the original change

Wait... is Cmocka using sizeof(tests)/sizeof(CMUnitTest) to find the number of tests to run? Is that what you intended the intention in commit 0b279e0? I suspect you might fix this faster yourself than spending the time explaining me how, but up to you.

I doubt anyone is using it here. We mostly have gcc 7/8 on our setups.

This memory corruption issue was reported by xtensa-apl-elf-gcc (crosstool-NG 1.23.0.440-3b8c) 7.3.0 built by merely following sof-docs + a couple test/cmocka cmake hacks.

Wait... is Cmocka using sizeof(tests)/sizeof(CMUnitTest) to find the number of tests to run? Is that what you intended in commit 0b279e0?

Yes it is, but it's not correct way to 'disable' test. I removed this test in another PR, author of KPB UTs will fix them in the future.

@mmaka1 I just realized "Internal Intel CI System/merge/build — Unit tests failed" (a.k.a. "quickbuild") was not reported at all here, any idea why? They were reported in (unrelated) PR #2581 so I took them for granted.

Unfortunately there is no static complete list of CI items that would contain 'not started yet' items (this was the case I guess). I hope it is possible to create one. I am confused too trying to guess the overall status when looking at the PRs with CI in progress.

Yes it is, but it's not correct way to 'disable' test. I removed this test in another PR,

#2598